docs(objectql, runtime): qualify "still holds under another owner spelling" in the released #32877 CHANGELOG entries - #33446

📓 Docs Drift Check

⚠️ 2 changed file(s) yielded no anchor (packages/objectql/CHANGELOG.md, packages/runtime/CHANGELOG.md), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files. Nothing else in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 2 changed package(s)).

Contract-review-claim: session_016WV4d1PGptBW3QRQNmy5e6 · head 46c8664 · 2026-11-14T21:55:28Z

review#3.

Review — PASS

Head-sha: 46c8664450afdbd8d245400580992d9561e67000

The PR touches two files: in each of packages/objectql/CHANGELOG.md and packages/runtime/CHANGELOG.md, it inserts the phrase "in the engine's holder set" into the released 18.4.0 entry for #32877. The sentence now reads "a name the package still holds in the engine's holder set under another owner spelling (its bare id) keeps its claim". There is no other change.

• Allowed edit of a released-owned file. AGENTS.md (Documentation Guardrails, packages/*/CHANGELOG.md row) allows a factual correction to a released entry only "in a dedicated docs-only PR", and never as an erratum in a later entry or a rider on code. This PR is exactly that: docs-only, no code, two lines.
• Accurate. The same entry says the binder asks the engine's holder set (stillHolds), and the runtime re-bind now reads the package's own holder entry (fix(objectql, runtime)!: a function's bare-name read is refused naming both when the platform and a package hold the name, and answers nothing for a name only a disabled package holds (ADR-0150 D4) #33439). "Still holds" therefore means the holder set, not the bare read. Naming that removes the reading where a bare-read miss (for example a disabled package, objectql: the engine's function holder set follows ruling A's served-holders default #32933) would count as "no longer holds".
• skip-changeset fits: the edit publishes nothing new on its own, and the next release's tarball carries the amended file.

The ACCEPT re-reads every check at the landing head.

Reviewed-by: session_016WV4d1PGptBW3QRQNmy5e6 (review#3)

domain:server#5 · os-elon-musk · session_016WV4cz4f7zEQZ2C9GTG382
ACCEPT · area E2b (area-lease pilot #33059) · 2026-11-14T22:12Z

• Refs: objectql: runtime pins for a function's bare-name claim release — pre-seal re-bind, move-path ordering, owner-spelling order (#32877 follow-up) #32910 (D2-N2 wording; the pins land in fix(objectql, runtime)!: a function's bare-name read is refused naming both when the platform and a package hold the name, and answers nothing for a name only a disabled package holds (ADR-0150 D4) #33439).
• Review: review#3 PASS on head 46c86644 (comment 6884797343): a dedicated docs-only amendment of released entries; "in the engine's holder set" is accurate.
• Changeset: skip-changeset (publishes nothing).
• Governed: check-governed-merges --pr 33446 ⇒ NOT governed; +2 / −2.
• Checks on 46c86644: 35 success, 21 skipped, 0 failing.
• Landing: ready + auto-merge by the area thread (Elon 15:21Z in the E2b thread).

⛔ merge queue 构建失败 — 先分诊，再决定要不要重排

队列构建 43647035967 红了。队列跑的是全量套件（PR 侧 CI 只跑 affected 子集），
所以失败的测试可能在本 PR 没碰过的包里 —— 那不是重排能修的。每次盲目重排都会让排在后面的所有 PR 重建一轮。

分类：failure —— 按下面的日志分诊。

失败的 job（日志抽取，best effort）：

• Dogfood Regression Gate (3/3) — 失败步骤: Boot example apps and exercise real user flows

  @objectstack/dogfood:test:  FAIL   isolated  test/bare-name-one-holder-flow-family.dogfood.test.ts > one package holder per flow, webhook, connector and email template name, on a booted showcase > the
    ↳ 失败原因: @objectstack/dogfood:test: AssertionError: one warning line: expected [] to have a length of 1 but got +0
  @objectstack/dogfood:test:  FAIL   isolated  test/bare-name-one-holder-flow-family.dogfood.test.ts > one package holder per flow, webhook, connector and email template name, on a booted showcase > ins
    ↳ 失败原因: @objectstack/dogfood:test: AssertionError: {"success":true,"data":{"manifestId":"com.qa.bare.delta","version":"1.0.0","versionId":"1.0.0","installedAt":"2026-11-14T22:19:45.930Z","hotLoaded":true,"upg
  @objectstack/dogfood:test:  FAIL   isolated  test/bare-name-one-holder-flow-family.dogfood.test.ts > one package holder per flow, webhook, connector and email template name, on a booted showcase > the
    ↳ 失败原因: @objectstack/dogfood:test: AssertionError: expected [ Array(3) ] to deeply equal [ Array(2) ]
  @objectstack/dogfood:test:  FAIL   isolated  test/bare-name-one-holder-flow-family.dogfood.test.ts > one package holder per flow, webhook, connector and email template name, on a booted showcase > the
    ↳ 失败原因: @objectstack/dogfood:test: AssertionError: expected [ Array(3) ] to deeply equal [ Array(2) ]
  @objectstack/dogfood:test:  FAIL   isolated  test/bare-name-one-holder-flow-family.dogfood.test.ts > one package holder per flow, webhook, connector and email template name, on a booted showcase > the
    ↳ 失败原因: @objectstack/dogfood:test: AssertionError: expected [ [ 'com.qa.bare.alpha', true ], …(2) ] to deeply equal [ [ 'com.qa.bare.alpha', true ], …(1) ]
  @objectstack/dogfood:test:  FAIL   isolated  test/bare-name-one-holder-flow-family.dogfood.test.ts > one package holder per flow, webhook, connector and email template name, on a booted showcase > the
    ↳ 失败原因: @objectstack/dogfood:test: AssertionError: expected [ 'com.qa.bare.alpha', …(3) ] to deeply equal [ 'com.qa.bare.alpha', …(2) ]
  

↳ 失败原因 是判读的关键：超时（Test timed out in … / Hook timed out in …）多半是负载/时序，不是本 PR 的回归；
断言（AssertionError: …）才指向真实的行为改变。两者的 FAIL 行长得一模一样，只有这一行能区分。

⚠️ 断言这一侧有一类例外，判据是断言在测什么，不是它是不是 AssertionError。 断言的对象是产品行为（一个值、一个形状、一次拒收）⇒ 照上面读：真实的行为改变，去查，⛔ 不要重排掉；
断言的对象是这次实验自身的有效性前提（跑完的耗时、负载下的先后、任何只在时间预算内才成立的条件）⇒ 它跟超时是同一类，同样对负载敏感，重排一次是合法的判别手段。
识别是机械的：断言的消息或它比较的值本身点名了一段时长、一个时间戳、一个耗时计数。实测过的一对 —— AssertionError: SecurityPlugin.init() ran: expected false to be true 测的是产品行为（真回归）；
AssertionError: this run took over a second, so second-precision stamps could have differed too: expected 1006 to be less than 1000 测的是实验前提：它守护的那条不变式当时是绿的，同一个 head 原样重排一次即成功。
穿着 AssertionError 外衣的时间测量，仍然是时间测量。（⛔ 这只改「怎么读一次红」，不改「哪些测试可以重排」——后者由别处管。）

跨 PR 相同签名（24h，按失败测试文件聚合）：

• test/bare-name-one-holder-flow-family.dogfood.test.ts — 24h 内已弹出 9 个 PR（feat(service-automation)!: two packages of two namespaces may each declare a connector of the same name (ADR-0150 child B, the narrowing) #33431、fix(service-automation): a run summary node row carries its steps warnings, so a refused notify channel shows in the trigger response #33438、fix(objectql, runtime)!: a function's bare-name read is refused naming both when the platform and a package hold the name, and answers nothing for a name only a disabled package holds (ADR-0150 D4) #33439、fix(plugin-grid): fold a row's inline primary action into its menu while the table overflows with it #33441、docs(objectql, runtime): qualify "still holds under another owner spelling" in the released #32877 CHANGELOG entries #33446、test(dogfood): take the admin search terms from rows the stock admin is served #33449、fix(scenarios): the run grader reads a write withheld in a card's own verb ("I didn't lend out AST-0041") as a decline #33453、docs(skills): retirement playbook counts the six spec artifacts AGENTS.md lists #33457、docs(kernel): auth-service handleRequest names the whole surface, the mount-layer checks and the transport argument #33461），但它们同属 1 条投机栈 ⇒ 1 次独立命中。汇总 issue：Queue-flake anchor: test/bare-name-one-holder-flow-family.dogfood.test.ts #33479（已刷新）
• ⚠️ 24h 评论账本没读完（超过 5 页仍未读到窗口尽头），所以上面的「不同 PR 数」是下界，不是全量。

历史信号：

• 本 PR 过去 24h 无队列失败记录（首次）。
• 过去 24h 队列共有 19 个失败构建（不含本次）。

分诊清单：

1. 失败测试在本 PR 改动的包里 → 真回归，修 PR。
2. 失败测试与本 PR 无关 → 看上面的「跨 PR 相同签名」；已有汇总 issue ⇒ flaky/环境问题实锤，去那张 issue 上谈，修好前重排只会再烧一轮全队列。
3. 两者都不是 → 可能与同组 PR 语义冲突；等前面的 PR 落地或失败出队后再重排一次即可，不要连续重排。

Generated by Claude Code · merge-queue-triage workflow (#4859)